Task: Analyze Propagation Request
This activity purpose is to analyze the feasability of propagating the changes among variants/core asset.
Disciplines: Change Management
Purpose
This activity purpose is to analyze the feasability of propagating the changes among variants/core asset.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
      Outputs
        Main Description

        Every PR must be analysed first in order to guarantee the correct propagation of the changes.

        The checks described in the "PR Analysis checklist" must be analysed in oder to approve the realization of a specific PR.

        The result of the anaylsis must be documented inside the PR, following the proposed "CCB Analysis documentation template".

        Steps
        Identify "from" where the changes are being propagated
        Verify if the "from" version of a certain changeset is compatible if the porduct/coreasset receiving the change.
        Identify the propagation type

        Two types of change propagation:

        - Complete Replacement: Where the changeset completly replaces the old version. In this type of propagation, much attention should be put into compatibility problems, and classical component upgrade problems, in order not to alter the right behavior of the system.

        - Merge versions: The whole changeset, or just a part of it, is merged against the already existing target version. In this case much attention should be put in merge conflicts resolution.

        [Optional] Isolate the changes to be propagated

        This step is only applicable in the Merge propagation type.

        In this case, it has to be identified what is the changeset (or part of it) that needs to be merged.

        Document the decision to propagate
         The result of the anaylsis must be documented inside the PR, following the proposed "CCB Analysis documentation template".
        More Information
        Checklists